home *** CD-ROM | disk | FTP | other *** search
- Path: druid.borland.com!rnelson
- From: uk.twyford.rnelson@wpo.borland.com (Roy Nelson)
- Newsgroups: comp.lang.c++
- Subject: Re: Oops. was Re: Problems with BC50
- Date: Thu, 28 Mar 96 16:07:56 GMT
- Organization: Borland
- Message-ID: <4jdrtm$akq@druid.borland.com>
- References: <4j4b8f$7u9@news.interpath.net> <4j4ge7$p24@news1.h1.usa.pipeline.com> <4j82ie$302@relay.cinvest.chel.su>
- NNTP-Posting-Host: rnelson.uk.borland.com
- X-Newsreader: News Xpress Version 1.0 Beta #4
-
- In article <4j82ie$302@relay.cinvest.chel.su>,
- xxx@relay.cinvest.chel.su (Valery Zhuravlev) wrote:
- >I also failed to build win16 application under BC50. Borland threw away
- >embedded in IDE linker for win16 (embedded linker works now only for win32).
- >So to build win16 application IDE transfers to standing alone tlink. And it
- >returns "out of memory". I don't know either how to avoid this problem.
- >
- >By the way - it works if you are running simple make-file generated by IDE.
- >Even just loaded 1.6 MB patch from ftp.borland.com for BC50 did not make this
- >work under IDE.
- >
- >larry
- >
- Hi Larry,
-
- From a previous message
- Here's an excerpt from the readme file:
-
- o) Building 16-Bit Applications in Windows 95
- ---------------------------------------------
- When you build 16-bit applications in the IDE, a process called
- CapDos32 remains in memory. If you view PVIEW.EXE, it shows
- these processes as WINOLDAP.
-
- To make these processes unload themselves after 16-bit builds,
- select \WINDOWS\SYSTEM\CONAGENT.EXE, select File | Properties, and
- check Close on exit on the Program page. To avoid running out of
- memory while linking 16-bit applications, set all memory choices
- to Auto on the Memory page of the CONAGENT.EXE properties.
-
- Roy Nelson
- Borland UK
-